Subject: NetBIOS Questions (Add_Group_Name)

From: "R. C. (Roy) Dixon" <[email-masked]>
Date: Wed, 15 Dec 93 09:16:33 EST

Reference:  Your note dated 09 December 1993

Paul,

Add_Group_Name_Query is encoded as a DATAFRAME, while Add_Name_Query
is encoded as a NETBIOS_ANQ message.

The NETBIOS_ANQ and NETBIOS_ANR messages are differentiated from the
other DATAGRAM messages since the IBM 6611 caches NetBIOS unique names
but does not cache group names.  This was an implementation decision,
not one dictated by architectural considerations.

The origin DLSw does not maintain local routing information upon the
receipt of Add_Group_Name_Query.  If a NETBIOS_ANR message is received
from a partner DLSw, the Add_Name_Recognized is transmitted as a
spanning tree explorer (STE) frame.  This represents a correction
to Table 6 in RFC 1434.

My thanks to you for bringing this to my attention.

Regards, Roy

---------------- Referenced NOTE ----------------------------------------
From: [email-masked] (Paul Brittain)
Subject: Netbios Add_Group_Name_Query handling
To: [email-masked]
Date: Thu, 9 Dec 93 14:55:50 GMT

Does anyone have answers to the following questions on Netbios
Add_Group_Name_Query handling?

It appears from the RFC that Add_Group_Name_Query frames are encoded
differently from Netbios Add_Name_Query frames (as DATAFRAMEs rather than
NETBIOS_ANQ) despite the fact that responses to both frame types (Netbios
Add_Name_Responses) must be handled identically by a DLS.

Is this correct?

If so, is the origin DLS expected to maintain local routing information
for DATAFRAME messages of this type to enable local routing of
NETBIOS_ANR message responses? Are retries of Add_Group_Name_Query frames
to be propagated or absorbed by the origin DLS?

Or are Add_Group_Name_Query frames intended to be encoded in NETBIOS_ANQ
messages and handled by a DLS in the same way as Add_Name_Query frames?

-------------------------------------------------------------------------